<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Whitepaper: The NUP Update for Service-Oriented Architecture</title>
<meta name="uma.type" content="Whitepaper">
<meta name="uma.name" content="the_rup_update_for_service-oriented_architecture">
<meta name="uma.presentationName" content="The NUP Update for Service-Oriented Architecture">
<meta name="element_type" content="other">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var backPath = './../../../';
					var imgPath = './../../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo,  '', false, false, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top"><a name="Top"></a>
<div id="page-guid" value="3.271868778372756E-306"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Whitepaper: The NUP Update for Service-Oriented Architecture</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../../images/whitepaper.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This paper describes an update to the Neusoft Unified Process (RUP) with the scope of introducing guidance for the software architect and designer in developing a service model, a model representing a portfolio of services that can be used as the basis for implementation tasks already in RUP.</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Related Elements</th><td class="sectionTableCell">
<ul>
<li>
<a href="./../../../rup/roles/rup_software_architect_DB0BF177.html" guid="{4AC346F0-E6FC-4D2C-8410-2EDF8DDDC91D}">软件架构师</a>
</li>
<li>
<a href="./../../../rup/capabilitypatterns/rup_software_architect_CB9312DF.html" guid="_xWYKs9x7Ed27Ld6FEj33Ng">软件架构师</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Description</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Main Description</th><td class="sectionTableCell"><p>
    By <a href="mailto:skjohn@us.ibm.com">Simon Johnston</a>, <a href="mailto:smithjo@us.ibm.com">John Smith</a>, IBM &copy;
    Copyright 2005 by IBM Corporation. All Rights Reserved.
</p>
<h3>
    Topics
</h3>
<ul>
    <li>
        <a href="#Motivation">Motivation</a>
    </li>
    <li>
        <a href="#Tour">Tour</a>
    </li>
</ul>
<h3>
    <a id="Motivation" name="Motivation">Introduction</a>
</h3>
<p>
    This paper describes an update to the Neusoft Unified Process (RUP) with the scope of introducing guidance for the
    <i><a class="elementLink" href="./../../../rup/roles/rup_software_architect_DB0BF177.html" guid="{4AC346F0-E6FC-4D2C-8410-2EDF8DDDC91D}">软件架构师</a></i> and <i><a class="elementLink" href="./../../../rup/roles/rup_designer_BA8DE74E.html" guid="{DB21F5EF-810B-4994-B120-79FA8774FA9D}">设计人员</a></i> in developing a <i><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_service_model_623494B9.html" guid="{E24679B7-19F1-483B-A1F1-578839C43888}">Service Model</a></i>, a model representing a portfolio of services that
    can be used as the basis for implementation tasks already in the RUP. It is also our intent to describe the connection
    between business modeling and the services model. Many Service-Oriented Architecture (SOA) projects use
    business-process models in understanding their business, functional requirements, and the services required to support
    a process.
</p>
<h4>
    <a id="Scope" name="Scope">Scope</a>
</h4>
<p>
    The scope of this update was addressed briefly in the introduction, but here are the set of requirements and scoping
    statements used to guide the project.
</p>
<ul>
    <li>
        <strong>Leverage the existing RUP;</strong> in this case it means that where possible we should describe new tasks
        and work products in relation to existing ones in the NUP and not unnecessarily add new concepts. Also, new
        elements should be added such that they fit into the overall flow of the RUP.
    </li>
    <li>
        <strong>Look forward to future tool capabilities;</strong> although the NUP is not tool dependent, it should be
        understood that there is no point in developing content in areas where no tooling will ever exist and then, there
        is no need to not write a topic because the tool is not in the market but we can expect it to be soon.
    </li>
    <li>
        <strong>Integration of other IBM experience in SOA;</strong> it is clear that other groups within IBM have
        experience that can be leveraged; harvested; and added to the concepts, guidelines, and practice we are
        introducing.
    </li>
    <li>
        <strong>Scope changes to Analysis & Design;</strong> we have looked at the literature that describes the
        application of SOA to business design and the implication of SOA on business models, operational organization, and
        business integration. We have also looked at the differences SOA tends to make on implementation, deployment, and
        operational management. This is too broad a scope for the first iteration so we have only focused on architecture
        and design issues.
    </li>
    <li>
        <strong>Deliver a foundation;</strong> this is the first iteration. We expect that additional guidance can be added
        to the framework presented here and the connection made between this content and the rest of the NUP in subsequent
        iterations.
    </li>
    <li>
        <strong>Look to changes that need to be made in the base, but defer to future release;</strong> we know that some
        concepts we introduce would fit better with terminology or other minor changes to the base RUP. While it would be
        desirable to change the RUP, that would have wider implications and would take far longer.
    </li>
</ul>
<h4>
    <a id="Decisions" name="Decisions">Key Decisions</a>
</h4>
<p>
    We intend that this content be a part of the base NUP in the next commercial release of the product. In the meantime,
    we want to make the content available to customers so content described here will be packaged as a NUP plugin and made
    available for download.
</p>
<p>
    In parallel, changes are being made to the Business Modeling (BM) discipline that would make the connection between BM
    and SOA stronger; however a decision was made to wait for the BM changes before completing the SOA plugin. The
    integration of both sets of changes will be made for the commercial release.
</p>
<p>
    A number of key ideas will be incorporated from the IGS <a href="http://www.ibm.com/developerworks/webservices/library/ws-soa-design1">Service-Oriented Modeling and Architecture
    (SOMA)</a>. While it is not possible to incorporate all the ideas and guidance in SOMA, mainly where it falls outside
    of the scope we set, it has been useful in guiding our work.
</p>
<p>
    Certain new principles have been introduced, including concepts that have affected the way we have approached the rest
    of the content, one of which is the concept of a service portfolio and an enterprise-wide view of the services provided
    in the enterprise.
</p>
<h4>
    <a id="Acknowledgements" name="Acknowledgements">Acknowledgements</a>
</h4>
<p>
    The authors would like to thank the following for their valuable contribution to this work. Alan Brown and Sky Matthews
    for their support and review of the content. Thanks to Eoin Lane, Steve Graham, Ed Kahan and Grant Larsen for providing
    not only comments on the work, but many examples that helped us and sometimes stumped us. We would also like to thank
    our colleagues working on the SOMA effort, Ali Arsanjani, Luba Cherbakov, and Kerrie Holley. Also we would like to
    thank Claus Torp Jensen of Danske Bank for his open and frank dialog on the bank's experience with applying SOA in the
    real world.
</p>
<h3>
    <a id="Tour" name="Tour">Tour</a>
</h3>
<p>
    The following table provides an overview of the areas affected by this update and focuses on a common logical
    progression through the existing and updated NUP material. The organization is by activity. These are the organizing
    constructs for a set of activities within a discipline so they already provide an organization familiar to most RUP
    users.
</p>
<table style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"  bordercolor="#808080" cellspacing="0" bordercolordark="#808080" cellpadding="4" width="100%" bordercolorlight="#808080" border="1">
    <colgroup>
        <col width="30%" />
        <col width="40%" />
        <col width="30%" />
    </colgroup>
    <tbody>
        <tr>
            <td align="middle">
                <strong>Activity</strong>&nbsp;
            </td>
            <td align="middle">
                <b>Comments</b> 
            </td>
            <td align="middle">
                <b>Supporting Topics</b> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/conceive_new_project_E9B31C9F.html" guid="{76FD7B68-FC91-488D-BBF1-6FE58DBACB87}">构思新项目</a> 
            </td>
            <td>
                The focus of the <a class="elementLinkWithType" href="./../../../rup/tasks/develop_business_case_F985B634.html" guid="{F7A5D34A-A8B1-466D-BE41-FFCD41B4430D}">Task: 开发商业理由</a> is adjusted to take into
                account that reusing existing internal and external services change the cost structure of development.
                Specifically, the cost of developing services decreases, but more effort is spent on identifying services
                and validating that selected services meet their requirements.
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup/tasks/develop_business_case_F985B634.html" guid="{F7A5D34A-A8B1-466D-BE41-FFCD41B4430D}">Task: 开发商业理由</a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">Concept: Service Oriented Architecture</a> <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_portfolio_52FD64AC.html" guid="1.851952881072508E-305">Concept: Service Portfolio</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLinkWithUserText" href="./../../../rup_bm/capabilitypatterns/Identify Business Processes_8B735C24.html" guid="_JnU6kTXEEdq4lJjndbo9Yw">Identify Business Processes</a> 
            </td>
            <td>
                In the <a class="elementLinkWithType" href="./../../../rup_bm/tasks/identify_business_goals_BDD1599E.html" guid="{BE3CF670-F2E7-4B03-90A0-F01B59777597}">Task: 确定业务目标</a>, the key forces that affect
                the business and the business strategy are outlined in terms of a model consisting of <a class="elementLinkWithUserText" href="./../../../rup_bm/workproducts/rup_business_goal_D99D08F9.html" guid="{6DC6732B-E7F1-495E-B5EC-AEBFD7BE80FE}">Work Product: Business Goals</a>. Therefore, it is important
                that these goals be connected to the services being developed to support the business. 
                <p>
                    The <a class="elementLinkWithType" href="./../../../rup_bm/tasks/find_business_actors_and_use_cases_2D0CD77E.html" guid="{1CCEB101-0027-451C-81CA-521D8B127F98}">Task: 查找业务参与者和用例 </a> is key in
                    identifying processes. It is during the realization of these <a class="elementLinkWithUserText" href="./../../../rup_bm/workproducts/rup_business_use_case_14F1BAF2.html" guid="{587A849E-B5F2-4B17-8C7F-1C59B0F5612D}">Work Product: Business Use Cases</a> that candidate
                    services may be identified from both process flows and <a class="elementLinkWithUserText" href="./../../../rup_bm/workproducts/rup_business_rule_9818835D.html" guid="{7F78B340-DD31-451A-9459-25F36E07401C}">Work Product: Business Rules</a> (see <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/identify_services_565F8B8A.html" guid="{0BF79161-A484-4C48-B72D-DA381DA05886}">Task: Identify Services</a>).
                </p>
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup_bm/tasks/identify_business_goals_BDD1599E.html" guid="{BE3CF670-F2E7-4B03-90A0-F01B59777597}">Task: 确定业务目标</a><br />
                <a class="elementLinkWithType" href="./../../../rup_bm/tasks/find_business_actors_and_use_cases_2D0CD77E.html" guid="{1CCEB101-0027-451C-81CA-521D8B127F98}">Task: 查找业务参与者和用例 </a><br />
                <a class="elementLinkWithType" href="./../../../rup_bm/tasks/maintain_business_rules_BFA8C64F.html" guid="{4BECA989-3039-45EE-858F-89077A154504}">Task: 维护业务规则 </a><br />
                <br />
                <a class="elementLinkWithUserText" href="./../../../rup_bm/workproducts/rup_business_goal_D99D08F9.html" guid="{6DC6732B-E7F1-495E-B5EC-AEBFD7BE80FE}">Work Product: Business Goals</a><br />
                <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_use_case_14F1BAF2.html" guid="{587A849E-B5F2-4B17-8C7F-1C59B0F5612D}">Artifact: 业务用例</a><br />
                <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_rule_9818835D.html" guid="{7F78B340-DD31-451A-9459-25F36E07401C}">Artifact: 业务规则</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLinkWithUserText" href="./../../../rup_bm/capabilitypatterns/explore_process_automation_B0DB879E.html" guid="_6B4PsTXDEdq4lJjndbo9Yw">Explore Process Automation</a> 
            </td>
            <td>
                The <a class="elementLinkWithType" href="./../../../rup_bm/tasks/define_automation_reqs_E0971AE5.html" guid="{E7491E4A-26FE-4CF1-8646-353DDBA3B9A5}">Task: 定义自动化需求</a> focuses on the
                derivation of system requirements from business modeling work products and specifically looks at the level
                of automation required to support a business activity. 
                <p>
                    It is also important that, as service-oriented solutions are more aligned with the business and
                    therefore the business architecture, the key elements of the IT services become reflected through to
                    the business.
                </p>
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup_bm/tasks/define_automation_reqs_E0971AE5.html" guid="{E7491E4A-26FE-4CF1-8646-353DDBA3B9A5}">Task: 定义自动化需求</a> 
            </td>
        </tr>
        <tr>
            <td>
                <p class="banner">
                    <a class="elementLink" href="./../../../rup/capabilitypatterns/manage_the_scope_of_the_system_7E0B34E5.html" guid="{CA9197A9-051E-4845-A7FC-2A8750BD8C02}">管理系统范围</a>
                </p>
            </td>
            <td>
                In the <a class="elementLinkWithType" href="./../../../rup/tasks/manage_dependencies_4F6CEFAA.html" guid="{7F42C4D6-584F-4B19-9B0B-FDE86BD85FBB}">Task: Manage Dependencies</a>, the requirements of the
                solution should be managed with the autonomy of services in mind. Services with fewer dependencies are more
                autonomous and therefore more reusable. 
                <p>
                    It is also important that services identified for a particular system are related to the existing
                    service portfolio, an enterprise-wide asset mapping out all services.
                </p>
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup/tasks/manage_dependencies_4F6CEFAA.html" guid="{7F42C4D6-584F-4B19-9B0B-FDE86BD85FBB}">Task: Manage Dependencies</a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_portfolio_52FD64AC.html" guid="1.851952881072508E-305">Concept: Service Portfolio</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/reports/service_dependencies_D8D49422.html" guid="1.2262765587812462E-305">Report: Service Dependencies</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/perform_architectural_synthesis_B63930B9.html" guid="{C67C8E56-D9B6-499C-8171-C153FB28F1C3}">执行架构合成</a> 
            </td>
            <td>
                In the <a class="elementLinkWithType" href="./../../../rup/tasks/architectural_analysis_2B9BE03.html" guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Task: 架构分析</a>, the existing description is
                changed somewhat by the introduction of a service focus. The survey of available assets is able to reuse
                the Service Portfolio models to gather information on existing services and their capabilities. Also, the
                development of the deployment overview has to take into account the middleware platforms to be used for
                service implementation and deployment. 
                <p>
                    The <a class="elementLinkWithType" href="./../../../rup/tasks/construct_arch_proof_145E3656.html" guid="{63D0BC8C-1FE9-48F7-9B03-B2394C11DCB5}">Task: 构建架构概念验证</a> can
                    also be valuable in comparing some of the distribution and message-design characteristics particular to
                    a service-oriented solution.
                </p>
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup/tasks/architectural_analysis_2B9BE03.html" guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Task: 架构分析</a><br />
                <a class="elementLinkWithType" href="./../../../rup/tasks/construct_arch_proof_145E3656.html" guid="{63D0BC8C-1FE9-48F7-9B03-B2394C11DCB5}">Task: 构建架构概念验证</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/solution_partitioning_352116F8.html" guid="1.6501323286225543E-305">Concept: Service Portfolio</a> <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">Concept: Service Oriented Architecture</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/refine_the_architecture_F40FA195.html" guid="{F2160C54-F666-4736-9982-FC7F58F15FAD}">优化架构</a> 
            </td>
            <td>
                The <a class="elementLinkWithType" href="./../../../rup/tasks/detail_software_requirements_A7F0A215.html" guid="{A1FA1E95-8028-42EB-9B92-0DA77380F3E1}">Task: 详细描述软件需求</a> also focuses on
                the technical and non-functional requirements and constraints imposed on the services that are either built
                or purchased. Specific non-functional requirements to consider are performance, security, infrastructure
                requirements, service dependencies, run-time licensing issues, and similar constraints that will influence
                service selection or construction. 
                <p>
                    The <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/identify_services_565F8B8A.html" guid="{0BF79161-A484-4C48-B72D-DA381DA05886}">Task: Identify Services</a> is where the set of candidate
                    services are identified from inputs such as the <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_analysis_model_9449F63A.html" guid="{CF53445C-3351-46C6-810E-8251830029A7}">Artifact: 业务分析模型</a>, the <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_goal_D99D08F9.html" guid="{6DC6732B-E7F1-495E-B5EC-AEBFD7BE80FE}">Artifact: 业务目标</a>, and <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_rule_9818835D.html" guid="{7F78B340-DD31-451A-9459-25F36E07401C}">Artifact: 业务规则</a>. The result is an service
                    model that contains a set of <a class="elementLinkWithUserText" href="./../../../rup_bm/workproducts/rup_business_use_case_14F1BAF2.html" guid="{587A849E-B5F2-4B17-8C7F-1C59B0F5612D}">Work Product:</a> <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_partn_DC19AD3F.html" guid="{C302AF5A-1591-4F26-94E5-C412866553BF}">Service Partitions</a> and <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_spec_37E89A91.html" guid="{20F06B5E-95D5-422C-AB68-7C213D28533A}">Work Product: Service Specifications</a>.
                </p>
                <p>
                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_partn_DC19AD3F.html" guid="{C302AF5A-1591-4F26-94E5-C412866553BF}">Work Product: Service Partitions</a> are used
                    extensively to develop maps and views of services, partitioning them according to both technical and
                    business categories. <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_collab_76358B24.html" guid="{9BBBE5B0-4D39-4555-9E20-0ADBD8327D29}">Work Product: Service Collaborations</a> are used to
                    identify services by analyzing the roles and responsibilities of collaborating candidate services.
                </p>
            </td>
            <td>
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/identify_services_565F8B8A.html" guid="{0BF79161-A484-4C48-B72D-DA381DA05886}">Task: Identify Services</a><br />
                <a class="elementLinkWithType" href="./../../../rup_soa_plugin/guidances/concepts/domain_design_77B2F855.html" guid="1.2602759670310655E-305">Concept: Domain Design</a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/solution_partitioning_352116F8.html" guid="1.6501323286225543E-305">Concept: Solution Partitioning</a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/domain_design_77B2F855.html" guid="1.2602759670310655E-305"><br />
                </a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_composition_and_choreography_41EDEECB.html" guid="7.723783423994501E-306">Concept: Service Composition and Choreography</a><br />
                <br />
                <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_analysis_model_9449F63A.html" guid="{CF53445C-3351-46C6-810E-8251830029A7}">Artifact: 业务分析模型</a><br />
                <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_goal_D99D08F9.html" guid="{6DC6732B-E7F1-495E-B5EC-AEBFD7BE80FE}">Artifact: 业务目标</a><br />
                <a class="elementLinkWithType" href="./../../../rup_bm/workproducts/rup_business_rule_9818835D.html" guid="{7F78B340-DD31-451A-9459-25F36E07401C}">Artifact: 业务规则</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_partn_DC19AD3F.html" guid="{C302AF5A-1591-4F26-94E5-C412866553BF}">Work Product: Service Partition</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_spec_37E89A91.html" guid="{20F06B5E-95D5-422C-AB68-7C213D28533A}">Work Product: Service Specification</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_collab_76358B24.html" guid="{9BBBE5B0-4D39-4555-9E20-0ADBD8327D29}">Work Product: Service Collaboration</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/design_components_13B33BFC.html" guid="{9C683674-97C1-4AEE-8DB0-9514AEFF698E}">设计组件</a> 
            </td>
            <td>
                During the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/soa_service_design_AB6BA763.html" guid="{9EB2B302-79F6-4DF8-AEB7-98E6AC1756DD}">Task: Service Design</a>, the candidate services identified
                in <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/identify_services_565F8B8A.html" guid="{0BF79161-A484-4C48-B72D-DA381DA05886}">Task: Identify Services</a> are refined, refactored, and
                developed into detailed models. Where the focus of the candidate <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_service_model_623494B9.html" guid="{E24679B7-19F1-483B-A1F1-578839C43888}">Work Product: Service Model</a> was to identify simply the
                specification for a set of possible services, the focus of the Service Design Model is adding the details
                of services, providers, and the collaborations between services. 
                <p>
                    Message Design, the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_message_BE931590.html" guid="{DD9F96C3-4D00-4441-951E-2674B9AEE1C6}">Work Product: Message</a> being used to describe the
                    data passed into and out of invocations of operations on services, also takes place at this point.
                </p>
                <p>
                    Whereas the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_collab_76358B24.html" guid="{9BBBE5B0-4D39-4555-9E20-0ADBD8327D29}">Work Product: Service Collaboration</a> was used during
                    identification to investigate the roles and responsibilities of services, within the design activity it
                    can be used to describe the implementation of a service as a collaboration or choreography of a set of
                    services.
                </p>
            </td>
            <td>
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/soa_service_design_AB6BA763.html" guid="{9EB2B302-79F6-4DF8-AEB7-98E6AC1756DD}">Task: Service Design</a> <br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_composition_and_choreography_41EDEECB.html" guid="7.723783423994501E-306">Concept: Service Composition and Choreography</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/state_management_for_services_E4156B50.html" guid="4.2228409903513537E-306">Guideline: State Management for Services</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/service_mediation_2F2C4C02.html" guid="2.5614739075754752E-306">Guideline: Service Mediation</a><br />
                <a class="elementLinkWithType" href="./../../../rup_soa_plugin/guidances/guidelines/service_CA5D991C.html" guid="2.1757522381974088E-306">Guideline: Service</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/message_design_DA8438ED.html" guid="5.580979266831891E-307">Concept: Message Design</a> <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_service_model_623494B9.html" guid="{E24679B7-19F1-483B-A1F1-578839C43888}">Work Product: Service Model</a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/message_design_DA8438ED.html" guid="5.580979266831891E-307"><br />
                </a><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_provider_C00D3410.html" guid="{8427751F-3C14-4CEB-9816-5112BDB91EED}">Work Product: Service Provider</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_service_1EE4C96C.html" guid="{FF65B0A2-6C53-4F01-9727-AACDB0D542C8}">Work Product: Service</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_chan_BB29CCA8.html" guid="{95AA7C70-6259-4627-B705-6A67E33A47BC}">Work Product: Service Channel</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_message_BE931590.html" guid="{DD9F96C3-4D00-4441-951E-2674B9AEE1C6}">Work Product: Message</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_svce_collab_76358B24.html" guid="{9BBBE5B0-4D39-4555-9E20-0ADBD8327D29}">Work Product: Service Collaboration</a><br />
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/design_components_13B33BFC.html" guid="{9C683674-97C1-4AEE-8DB0-9514AEFF698E}">设计组件</a> (Realization)
            </td>
            <td>
                <p>
                    The <a class="elementLinkWithType" href="./../../../rup/tasks/subsystem_design_5D1BCC0C.html" guid="{CAA385CA-2BA2-40F2-8FE3-E21089D02119}">Task: 子系统设计</a> further
                    refines the design of the service, identifying subsystems within the service which provide the real
                    behavior of the service. In the early stages of the Elaboration phase, there is likely to be a single
                    component which acts as a stub to simulate the behavior of the service for architectural prototyping
                    purposes. The behavior of this component is later distributed to a collaboration of classes contained
                    within the subsystem.
                </p>
                See the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">Concept: Service-Oriented Architecture</a> for more detail on the
                relationship between Services, Components, and Classes.
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup/tasks/subsystem_design_5D1BCC0C.html" guid="{CAA385CA-2BA2-40F2-8FE3-E21089D02119}">Task: 子系统设计</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/state_management_for_services_E4156B50.html" guid="4.2228409903513537E-306">Guideline: State Management for Services</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/going_from_services_to_service_components_914EA328.html" guid="2.4211910729992714E-305">Guideline: Going from Services to Service Components</a><br />
                <br />
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_component_E259F3CC.html" guid="{447385A0-E565-4C87-A082-402AF21CA088}">Work Product: Service Component</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/design_the_database_2BE59DB0.html" guid="{FB3EB753-A979-4849-B57B-97F39271F82B}">设计数据库</a> 
            </td>
            <td>
                The focus in elaboration is on ensuring that the service encapsulates its data requirements completely and
                that dependencies between services do not arise due to the introduction of services that should be using
                the same data source. For more information, see the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/service_data_encapsulation_F424F20E.html" guid="1.6727924656888407E-305">Guideline: Service Data Encapsulation</a>.
            </td>
            <td>
                <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/domain_design_77B2F855.html" guid="1.2602759670310655E-305">Guideline: Domain Design Guideline: Service Data Encapsulation</a> 
            </td>
        </tr>
        <tr>
            <td>
                <a class="elementLink" href="./../../../rup/capabilitypatterns/implement_components_AFD1799D.html" guid="{4DC6F53E-1FE1-44EE-812B-003D3BD1ACEA}">实现组件</a> 
            </td>
            <td>
                <p>
                    It is important to realize that the move toward development of service-oriented solutions does not
                    invalidate the lessons learned from developing component-based solutions. In fact, components are used
                    as the implementation artifacts for services. This can be accomplished in two ways, as described below,
                    but in either case the approach taken during <a class="elementLinkWithType" href="./../../../rup/tasks/implement_component_AE366827.html" guid="{3293F4F7-EFCD-4476-BFF1-81AC3812B512}">Task: 实现设计元素</a> will depend on the
                    runtime platform chosen.
                </p>
                <ul>
                    <li>
                        From the service model, generate web service artifacts such as Web Services Description Language
                        (WSDL 1.1) which acts as a description of a service interface as well as the information about the
                        location and protocols used to access an instance of a service. From these artifacts, most design
                        tools can generate both server stubs and client accessors for the specified service.
                    </li>
                    <li>
                        From the service model, transform into either a System <a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_usecase_model_EF15E534.html" guid="{9C66F2EC-EDEB-4369-9AFB-04B9E7CBCB8E}">Work Product: Use Case Model</a> or a <a class="elementLinkWithType" href="./../../../rup/workproducts/rup_design_model_2830034D.html" guid="{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}">Artifact: 设计模型</a> that can be further
                        refined to describe the implementation before generating either an <a class="elementLinkWithType" href="./../../../rup/workproducts/rup_implementation_model_5858DB65.html" guid="{157E9B67-C619-410D-A927-F2CD217BF8FE}">Artifact: 实现模型</a> or
                        programming language artifacts that represent the service implementation.
                    </li>
                </ul>
            </td>
            <td>
                <a class="elementLinkWithType" href="./../../../rup/tasks/implement_component_AE366827.html" guid="{3293F4F7-EFCD-4476-BFF1-81AC3812B512}">Task: 实现设计元素</a><br />
                <a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_usecase_model_EF15E534.html" guid="{9C66F2EC-EDEB-4369-9AFB-04B9E7CBCB8E}">Work Product: Use Case Model</a><br />
                <a class="elementLinkWithType" href="./../../../rup/workproducts/rup_design_model_2830034D.html" guid="{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}">Artifact: 设计模型</a><br />
                <a class="elementLinkWithType" href="./../../../rup/workproducts/rup_implementation_model_5858DB65.html" guid="{157E9B67-C619-410D-A927-F2CD217BF8FE}">Artifact: 实现模型</a> 
            </td>
        </tr>
    </tbody>
</table>
<br /></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script type="text/javascript" language="JavaScript">
				contentPage.onload();
			</script>
</html>
